System and Framework for Transforming Domain Data

ABSTRACT

Methods, systems, and computer-readable media for transforming or modifying domain data are provided. A master control table may be generating including data from a plurality of domain data tables and a configuration associated with each domain data table. A user may modify a domain data table (or associated domain data) via the master control table. A user interface may be generated having a first portion, listing domain data tables in the master control table, and a second portion. Upon selection of a domain data table from the first portion, the second portion may be populated with the data and associated configuration of the selected domain data table. Modifications to the domain data table (and/or domain data) may be made via the second portion.

BACKGROUND

Aspects of the disclosure relate to computer hardware and software. Inparticular, one or more aspects of the disclosure generally relate tocomputer hardware and software for dynamically transforming domain data.

Organizations, such as corporate entities and other large enterpriseorganizations, often store and implement data tables to facilitate useof one or more user interfaces (e.g., by a user via an on-line website,mobile application, or the like). The number of data tables may beextremely large and the number of users accessing the data storedtherein may be tremendous. Accordingly, as changes (e.g., to a userinterface) are desired or requested, an existing data table may requiremodification or a new data table may need to be created. This can beinefficient for the system, cause excessive use of system resources,and/or result in inaccuracies. Accordingly, a system and framework fordynamically modifying one or more data tables.

SUMMARY

The following presents a simplified summary in order to provide a basicunderstanding of some aspects of the disclosure. The summary is not anextensive overview of the disclosure. It is neither intended to identifykey or critical elements of the disclosure nor to delineate the scope ofthe disclosure. The following summary merely presents some concepts ofthe disclosure in a simplified form as a prelude to the descriptionbelow.

Aspects of the disclosure relate to computer systems that provideeffective, efficient, and accurate ways of modifying domain data. Insome examples, domain data tables may be aggregated or consolidated. Amaster control table may be generated including data from the domaindata tables, as well as any configurations, definitions, types of data,and the like, associated with each table.

In some examples, a user interface may be generated. The user interfacemay include at least a first portion and a second portion. The firstportion may be populated with a listing of available domain data tables.The first portion may be populated from the master control table. Uponselection of a domain data table, the second portion of the userinterface may be populated. Populating the second portion may includedisplaying the data associated with the selected table, as well as theassociated configuration, and the like. A user may them transform ormodify the domain data via the master control table (e.g., via thesecond portion of the user interface). Any transformations ormodifications may be implemented by refreshing the master control table.

These features, along with many others, are discussed in greater detailbelow.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure is illustrated by way of example and not limitedin the accompanying figures in which like reference numerals indicatesimilar elements and in which:

FIG. 1 depicts an illustrative operating environment in which variousaspects of the disclosure may be implemented in accordance with one ormore aspects described herein;

FIG. 2 depicts an illustrative block diagram of workstations and serversthat may be used to implement the processes and functions of certainaspects of the present disclosure in accordance with one or more aspectsdescribed herein;

FIG. 3 depicts an illustrative computing platform for transformingdomain data in accordance with one or more aspects described herein;

FIG. 4 depicts an illustrative event sequence for generating a mastercontrol table in accordance with one or more aspects described herein;

FIGS. 5A-5E depict an illustrative event sequence for modifying a domaindata table and/or associated data via the master control table accordingto one or more aspects described herein;

FIG. 6 depicts an illustrative method for generating a master controltable and modifying domain data via the master control table accordingto one or more aspects described herein; and

FIGS. 7A and 7B depict an illustrative user interface having a firstportion and a second portion for modifying domain data according to oneor more aspects described herein.

DETAILED DESCRIPTION

In the following description of various illustrative embodiments,reference is made to the accompanying drawings, which form a parthereof, and in which is shown, by way of illustration, variousembodiments in which aspects of the disclosure may be practiced. It isto be understood that other embodiments may be utilized, and structuraland functional modifications may be made, without departing from thescope of the present disclosure.

It is noted that various connections between elements are discussed inthe following description. It is noted that these connections aregeneral and, unless specified otherwise, may be direct or indirect,wired or wireless, and that the specification is not intended to belimiting in this respect.

As discussed herein, entities that support one or more applications(e.g., online applications, mobile applications, and the like) may relyon a plurality of domain data tables. Often the domain data tables arenumerous and can be cumbersome and inefficient to modify. This may makeimplementing changes to one or more user interfaces associated with theapplication inefficient and prone to inaccuracies. Accordingly, thearrangements described herein include generating a master control tableincluding data from a plurality of domain data tables. A configurationassociated with each domain data table may also be stored by the mastercontrol table.

Upon receiving a request to modify a user interface or a domain datatable (or associated data) the system may generate a user interfacehaving a first portion and a second portion. The first portion mayinclude a listing of domain data tables from the master control table.Upon selection of a domain data table from the first portion, the secondportion may be populated with the data and associated configuration ofthe selected domain data table. Accordingly, a user may modify theselected domain data table in the second portion and those modificationsmay be implemented upon refreshing the master control table. Thesearrangements provide an efficient way of modifying domain data tablesand aids in standardizing changes made.

These and various other aspects and features will be described morefully herein.

FIG. 1 depicts an illustrative operating environment in which variousaspects of the present disclosure may be implemented in accordance withone or more example embodiments. Referring to FIG. 1, computing systemenvironment 100 may be used according to one or more illustrativeembodiments. Computing system environment 100 is only one example of asuitable computing environment and is not intended to suggest anylimitation as to the scope of use or functionality contained in thedisclosure. Computing system environment 100 should not be interpretedas having any dependency or requirement relating to any one orcombination of components shown in illustrative computing systemenvironment 100.

Computing system environment 100 may include domain data modificationcomputing device 101 having processor 103 for controlling overalloperation of domain data modification computing device 101 and itsassociated components, including random-access memory (RAM) 105,read-only memory (ROM) 107, communications module 109, and memory 115.Domain data modification computing device 101 may include a variety ofcomputer readable media. Computer readable media may be any availablemedia that may be accessed by domain data modification computing device101, may be non-transitory, and may include volatile and nonvolatile,removable and non-removable media implemented in any method ortechnology for storage of information such as computer-readableinstructions, object code, data structures, program modules, or otherdata. Examples of computer readable media may include random accessmemory (RAM), read only memory (ROM), electronically erasableprogrammable read only memory (EEPROM), flash memory or other memorytechnology, compact disk read-only memory (CD-ROM), digital versatiledisks (DVD) or other optical disk storage, magnetic cassettes, magnetictape, magnetic disk storage or other magnetic storage devices, or anyother medium that can be used to store the desired information and thatcan be accessed by domain data modification computing device 101.

Although not required, various aspects described herein may be embodiedas a method, a data processing system, or as a computer-readable mediumstoring computer-executable instructions. For example, acomputer-readable medium storing instructions to cause a processor toperform steps of a method in accordance with aspects of the disclosedembodiments is contemplated. For example, aspects of method stepsdisclosed herein may be executed on a processor on domain datamodification computing device 101. Such a processor may executecomputer-executable instructions stored on a computer-readable medium.

Software may be stored within memory 115 and/or storage to provideinstructions to processor 103 for enabling domain data modificationcomputing device 101 to perform various functions. For example, memory115 may store software used by domain data modification computing device101, such as operating system 117, application programs 119, andassociated database 121. Also, some or all of the computer executableinstructions for domain data modification computing device 101 may beembodied in hardware or firmware. Although not shown, RAM 105 mayinclude one or more applications representing the application datastored in RAM 105 while domain data modification computing device 101 ison and corresponding software applications (e.g., software tasks) arerunning on domain data modification computing device 101.

Communications module 109 may include a microphone, keypad, touchscreen, and/or stylus through which a user of domain data modificationcomputing device 101 may provide input, and may also include one or moreof a speaker for providing audio output and a video display device forproviding textual, audiovisual and/or graphical output. Computing systemenvironment 100 may also include optical scanners (not shown). Exemplaryusages include scanning and converting paper documents, e.g.,correspondence, receipts, and the like, to digital files.

Domain data modification computing device 101 may operate in a networkedenvironment supporting connections to one or more remote computingdevices, such as computing devices 141, 151, and 161. Computing devices141, 151, and 161 may be personal computing devices or servers thatinclude any or all of the elements described above relative to domaindata table modification computing device 101. Computing device 161 maybe a mobile device (e.g., smart phone) communicating over wirelesscarrier channel 171.

The network connections depicted in FIG. 1 may include local areanetwork (LAN) 125 and wide area network (WAN) 129, as well as othernetworks. When used in a LAN networking environment, domain datamodification computing device 101 may be connected to LAN 125 through anetwork interface or adapter in communications module 109. When used ina WAN networking environment, domain data modification computing device101 may include a modem in communications module 109 or other means forestablishing communications over WAN 129, such as Internet 131 or othertype of computer network. The network connections shown are illustrativeand other means of establishing a communications link between thecomputing devices may be used. Various well-known protocols such astransmission control protocol/Internet protocol (TCP/IP), Ethernet, filetransfer protocol (FTP), hypertext transfer protocol (HTTP) and the likemay be used, and the system can be operated in a client-serverconfiguration to permit a user to retrieve web pages from a web-basedserver. Any of various conventional web browsers can be used to displayand manipulate data on web pages.

The disclosure is operational with numerous other computing systemenvironments or configurations. Examples of well-known computingsystems, environments, and/or configurations that may be suitable foruse with the disclosed embodiments include, but are not limited to,personal computers (PCs), server computers, hand-held or laptop devices,smart phones, multiprocessor systems, microprocessor-based systems, settop boxes, programmable consumer electronics, network PCs,minicomputers, mainframe computers, distributed computing environmentsthat include any of the above systems or devices, and the like.

FIG. 2 depicts an illustrative block diagram of workstations and serversthat may be used to implement the processes and functions of certainaspects of the present disclosure in accordance with one or more exampleembodiments. Referring to FIG. 2, illustrative system 200 may be usedfor implementing example embodiments according to the presentdisclosure. As illustrated, system 200 may include one or moreworkstation computers 201. Workstation 201 may be, for example, adesktop computer, a smartphone, a wireless device, a tablet computer, alaptop computer, and the like. Workstations 201 may be local or remote,and may be connected by one of communications links 202 to computernetwork 203 that is linked via communications link 205 to domain datatable modification server 204. In system 200, domain data tablemodification server 204 may be any suitable server, processor, computer,or data processing device, or combination of the same. Domain data tablemodification server 204 may be used to process the instructions receivedfrom, and the transactions entered into by, one or more participants.

Computer network 203 may be any suitable computer network including theInternet, an intranet, a wide-area network (WAN), a local-area network(LAN), a wireless network, a digital subscriber line (DSL) network, aframe relay network, an asynchronous transfer mode (ATM) network, avirtual private network (VPN), or any combination of any of the same.Communications links 202 and 205 may be any communications linkssuitable for communicating between workstations 201 and domain datatable modification server 204, such as network links, dial-up links,wireless links, hard-wired links, as well as network types developed inthe future, and the like.

FIG. 3 depicts an environment 300 including an illustrative computingplatform for modifying domain data via a master control table accordingto one or more aspects described herein. For instance, the environment300 includes a domain data modification computing platform 310, whichmay include one or more processors 311, memory 312, and communicationinterface 318. A data bus may interconnect processor(s) 311, memory 312,and communication interface 318. Communication interface 318 may be anetwork interface configured to support communication between domaindata modification computing platform 310, and one or more networks(e.g., network 330). Memory 312 may include one or more program moduleshaving instructions that when executed by processor(s) 311 cause domaindata modification computing platform 310 to perform one or morefunctions described herein and/or one or more databases that may storeand/or otherwise maintain information which may be used by such programmodules and/or processor(s) 311. In some instances, the one or moreprogram modules and/or databases may be stored by and/or maintained indifferent memory units of the domain data modification computingplatform 310 and/or by different computer systems that may form and/orotherwise make up the domain data modification computing platform 310.

For example, memory 312 may include a domain data table module 313. Thedata table module 313 may include hardware and/or software configured toperform various functions within the domain data modification computingplatform. For instance, the data table module 313 may generate and/orstore (e.g., in a database within the module) one or more domain datatables and/or configurations associated therewith. For instance, domaindata tables that are currently available may be stored in the data tablemodule 313. Further, a number of columns, types of data within eachtable, and the like, may be stored in the data table module 313.

In existing systems, modifying one or more domain data tables mayrequire modifying the code associated with a particular data table.However, it is desirable to be able to dynamically modify the userinterfaces which draw data from the one or more domain data tables. Forinstance, a website may have a plurality of user interfaces with variousdifferent options (e.g., from a drop down or other menu), may rely onvarious sources for verification of data, and the like. In order tochange these user interfaces (and/or sources, and the like), the domaindata table may be modified. However, the ability to dynamically modifyone or more domain data tables (or data associated therewith) via amaster control table, as discussed herein, creates a more efficientcomputing system since it reduces or eliminates the need for hard codedchanges to a desired data table.

Memory 312 may further include a master control table module 314. Themaster control table module 314 may include hardware and/or softwareconfigured to perform various functions within the domain datamodification computing platform 310. For instance, the master controltable module 314 may receive data from the data table module 313 and maygenerate a master control table. The master control table may includesome or all of the data from the plurality of domain data tables storedin the data table module 313, as well as configuration information(e.g., type of data, number of columns, and the like) associated witheach domain data table stored in the data table module 313. Accordingly,as will be discussed more fully herein, the master control table mayenable a user to dynamically modify a domain data table (or dataassociated therewith) via a user interface providing data from themaster control table.

The memory 312 may also include a modification module 315. Themodification module 315 may include hardware and/or software configuredto perform various functions within the domain data modificationcomputing platform 310. For instance, the modification module 315 mayreceive requested modifications to a user interface, an associateddomain data table, or the like. The requested modification may bereceived from, for example, a user computing device 302. The usercomputing device 302 may be one of various types of devices, such as amobile device, laptop computing device, desktop computing device, tabletcomputing device, and the like.

Various types of modifications may be requested. For instance, asdiscussed above, the domain data tables may be used to generate one ormore user interfaces (e.g., for an on-line or mobile application, or thelike). The one or more user interfaces may include various settings,options, and the like. Modifications to any of these settings, timeouts, sources used to verify data based on input received via the userinterface, menu options, and the like, may be requested via themodification module 315. The modification module 315 may then be used,in conjunction with various other components of the domain datamodification computing platform 310, to facilitate the requestedmodification, as will be discussed more fully herein.

Domain data modification computing platform 310 may further include anauthentication module 316. The authentication module 316 may includehardware and/or software configured to perform various functions withinthe domain data modification computing platform 310. For instance,modifications to domain data may be restricted to authorized users.Accordingly, upon a modification being requested, the authenticationmodule 316 may confirm that the requesting user is authorized to makeone or more changes or modifications. In some examples, theauthentication module 316 may store a list of authorized users includinga name, employee number or other unique identifier, a username, apassword or personal identification number, biometric data, and thelike. This information may be compared with login or authenticationinformation provided during the modification request process in order todetermine whether the user is authorized to make a modification (andtherefore enable or permit modification) or is not authorized, andthereby prevent modifications.

The domain data modification computing platform 310 may further includea user interface generating module 317. The user interface generatingmodule 317 may include hardware and/or software configured to performvarious functions within the domain data modification computing platform310. For instance, the user interface generating module 317 may generatea user interface that may be used to facilitate requested modifications.For instance, the user interface module 317 may generate a modificationuser interface having two portions. The first portion may include alisting of available domain data tables that may be modified. The secondportion may include, upon selection of a domain data table from thefirst portion, a display of the domain data table with associatedconfigurations, and the like. The user interface may be generated fromthe master control table which includes all of the domain data tablesand associated configurations. Accordingly, the system may generate theuser interface, and display associated data, using information providedfrom the master control table (e.g., without retrieving informationfrom, accessing, or the like, each individual domain data table).

In some examples, the user interface generating module 317 may alsogenerate one or more user interfaces for use in the application whichrelies on the domain data tables. That is, a user interface for which amodification is requested may be generated by the user interfacegenerating module 317 upon implementation of the modification. Thegenerated user interface may then include the modification made to thedomain data via the master control table, as will be discussed morefully herein.

FIG. 4 depicts an illustrative event sequence for generating a mastercontrol table that may be used to facilitate modifications to domaindata and/or one or more associated user interfaces according to one ormore aspects described herein. It should be noted that the events shownand described with respect to FIG. 4 are merely one example sequence andsome steps may be omitted, or additional steps added, without departingfrom the invention.

In step 401, data associated with one or more domain data tables may bereceived, such as via a user computing device 302. In some examples,receiving the data may include uploading or coding information that maybe used to create a domain data table. In step 402, the received datamay be transmitted to the domain data table module 313 and, in step 403,one or more domain data tables may be generated.

In some examples, domain data tables might already have been generatedor may already exist. In these arrangements, steps 401-403 may beomitted.

In step 404, domain data table information may be transmitted to themaster control table module 314. The domain data table information mayinclude the data associated with each domain data table, as well asconfiguration information associated with each domain data table. Instep 405, the transmitted domain data table information may be receivedby the master control table module 314.

In step 406, the master control table may be generated. Generating themaster control table may include aggregating or compiling the receiveddomain data table information including data and configurationinformation. This aggregated or compiled information may be stored inthe master control table in order to facilitate dynamic modification ofthe data (and associated user interfaces). That is, modifications to anyof the domain data tables associated with the master control table maybe performed via the master control table without accessing or directlymodifying the domain data table being modified. Rather, the modificationmay be made via the master control table and the modified data may bestored therein.

FIGS. 5A-5E depict an illustrative event sequence for modifying domaindata via the master control table according to one or more aspectsdescribed herein. It should be noted that the events shown and describedwith respect to FIGS. 5A-5E are merely one example sequence and somesteps may be omitted, or additional steps added, without departing fromthe invention.

With reference to FIG. 5A, in step 501, a request to modify a userinterface, a domain data table (and/or associated domain data), and/oradd a new domain data table may be received. The request may be receivedfrom a user computing device, such as user computing device 302 in FIG.3. As discussed herein, the requested modification may include a requestto modify one or more of a setting, a menu option, a source used toverify data, and the like. In some examples, the requested modificationmay be associated with more than one user interface (e.g., a series ofuser interfaces associated with an application being implemented on acomputing device), multiple domain data tables, and the like.

In step 502, the requested modification may be transmitted to the domaindata modification computing platform 310. In response to the request,the domain data modification computing platform 310 may transmit arequest for authentication information to the user computing device 302in step 503. In some examples, the request for authenticationinformation may be transmitted from the authentication module 316 withinthe domain data modification computing platform 310.

In step 504, login and/or authentication information may be received bythe user computing device 302 and transmitted to the authenticationmodule 316 of the domain data modification computing platform 310 instep 505. The login/authentication information may include a usernameand password combination, personal identification number, biometric dataof the user, and the like.

In step 506, the user may be authenticated by, for instance, theauthentication module 316 of the domain data modification computingplatform 310. For instance, the received login/authenticationinformation may be compared to pre-stored login/authenticationinformation for authorized users to determine whether the userrequesting the modification is an authorized user. If so, the processmay continue to FIG. 5B. If not, the process may end and, in someexamples, the requesting user may be notified that the providedlogin/authentication information did not match pre-stored informationfor authorized users.

For instance, with reference to FIG. 5B, at step 507, the authenticationresults may be transmitted from the domain data modification computingplatform 310 to the user computing device 302. The results may bedisplayed on the user computing device and may indicate whether thelogin/authentication information was authenticated.

In step 508, the master control table may be retrieved (e.g., from themaster control table module 314). In step 509, a modification userinterface may be generated having two portions. For instance, the userinterface generating module 317, may generate a modification userinterface that includes a first portion and a second portion. In step510, the first portion of the generated modification user interface maybe populated with a listing of available domain data tables retrievedfrom the master control table. That is, the generated modification userinterface may be generated using data from the master control table inorder to efficiently and dynamically modify data, user interfaces, andthe like.

In step 511, the generated modification user interface with the firstportion populated may be transmitted to the user computing device 302.As indicated herein, the first portion may include a listing of alldomain data tables available for modification. The generatedmodification user interface with the first portion populated may bedisplayed on the user computing device in step 512.

With reference to FIG. 5C, at step 513, user input selecting a datatable for modification from the listing provided in the first portion ofthe modification user interface is received. The selection may betransmitted to the domain data modification computing platform 310 instep 514.

In response to the selection, the domain data modification computingplatform 310 (e.g., a user interface generating module 317) may generatea modification user interface similar to the modification user interfacepreviously generated but with the second portion populated as well instep 515. That is, selection of a domain data table from the firstportion may cause the user interface to display the domain data table(e.g., data, configurations, and the like) in the second portion of theuser interface. The data used to populate the second portion may beretrieved from the master control table (e.g., without accessing theselected domain data table itself). Populating the second portion mayinclude displaying the data table in the configuration associated withthat data table. For instance, the data, type of data, number ofcolumns, and the like, may be displayed based on the data retrieved fromthe master control table.

In step 516, the revised or regenerated modification user interface withthe first portion and second portions populated may be transmitted tothe user computing device 302. With reference to FIG. 5D, themodification user interface may be displayed on the user computingdevice 302 in step 517.

In step 518, user input may be received modifying the selected domaindata via the second portion of the user interface. That is, a user maymodify one or more attributes or features (e.g., data, configurations,and the like) displayed in the second portion. The modification may betransmitted to the domain data modification computing platform 310 instep 519 and, in some examples, the master control table may be updatedwith the modification in step 520. For instance, in arrangements inwhich the requested modification is a modification to a user interface,the master control table may be updated with the modification in step520. Modifying the master control table may cause the domain data to bemodified without requiring a coded modification to the selected domaindata table. Accordingly, changes may be made dynamically, efficiently,and in a standardized manner.

With reference to FIG. 5E, the master control table may be refreshed instep 521. In some examples, the master control table may be refreshedautomatically in response to modifications being made, completed,detected, or the like. Refreshing the master control table may implementthe modifications made and may cause the system to generate one or morerevised user interfaces in step 522. The revised user interfaces may bethose associated with the application for which the modification wasrequested. In step 523, the modified user interface(s) (e.g., updatedapplication) may be transmitted to the user computing device 302 in step523 and may be displayed to the user in step 524.

FIG. 6 illustrates one example method of dynamically modifying ortransforming domain data in accordance with one or more aspectsdescribed herein. In step 600, a plurality of domain data tables may bereceived. The received domain data tables may be in one or more formats.In some example, the receive domain data tables may be reformatted to beread by a master control table. For instance, one or more domain datatables may be evaluated to determine a format associated with the domaindata table. If the format does not match one or more formats configuredto be read by the master control table, the domain data table may bereformatted to a format configured to be read by the master controltable. The domain data tables may include differing numbers of columns,types of data, or the like.

In step 602, the domain data tables may be stored. For instance, thesystem may store the plurality of domain data tables for use ingenerating user interfaces that may be accessed by, interacted with, orthe like, one or more users via, for instance, an on-line application orwebpage, a mobile application, or the like.

In some examples, one or more domain data tables may be created from orvia the master control table. In such examples, steps 600 and 602 may beomitted. Additionally or alternatively, some domain data tables may begenerated and stored while others may be created via the master controltable.

In step 604, a master control table may be generated. The master controltable may include a common framework listing all of the plurality ofdomain data tables received and/or stored. The master control table mayinclude code that is generic and may store configurations for each ofthe domain data tables associated with the master control table. Forinstance, the master control table may be able to read theconfigurations of each domain data table (such as number of columns,types of data, or the like) and may understand the structure,configuration, or the like, of each domain data table. Thus, theconfiguration of each domain data table may be stored in associationwith the master control table, which may enable changes to any of thedomain data tables to be made via the master control table, as will bediscussed more fully below.

In step 606, a request may be received to modify an existing userinterface (e.g., an interface generated from one or more domain datatables associated with the master control table), a domain data table,or the like. The request may include a request to add an additionaloption to a drop-down menu, modify one or more settings associated withoptions on the user interface, add an additional source for verifyingdata input into the user interface, modify one or more time outsassociated with the user interface, or the like.

In step 608, the user requesting to modify the user interface may accessthe domain data modification system and may be authenticated by thesystem, as discussed herein. Upon determining that the user isauthorized to access the domain data modification system, a userinterface having a first portion and a second portion may be generatedand displayed to the user in step 610. Generating the user interface mayinclude generating the first portion and the second portion andpopulating the first portion based on data retrieved from the mastercontrol table. In some examples, the first portion may include a listingof all domain tables associated with the master control table.Populating the first portion may include retrieving the master controltable entries (e.g., reading the domain tables from the master controltable) to determine data content, type of columns, types of columns, andother specifications and/or configurations of each domain table. In someexamples, this information may be transferred from one or more datastores to the system to populate the first portion of the interface.

In step 612, a domain table may be selected from the first portion.Selection of the domain table from the first portion may populate thesecond portion (e.g., the system may generate another user interface,update the existing user interface, or the like) with a display of theselected domain data table (e.g., number of columns, types of columns,data, and the like) in step 614. Displaying the domain table may includecalling up data that was previously transferred to the system in thepopulating of the first portion of the user interface.

In step 616, a transformation of data associated with the selecteddomain data table may be made. For instance, a user may modify or edit aportion of the data table (e.g., data within the table, number ofcolumns, types of columns, or the like). The transformation of the datamay be performed in the second portion of the user interface and, insome examples, may cause data to be transformed within the mastercontrol table.

In step 618, in at least some examples, the master control table may berefreshed. For instance, when a requested modification (e.g., amodification requested in, for example, step 606) is a request to modifya user interface, the master control table may be refreshed or updatedin step 618. Refreshing the master control table may cause anytransformations or modifications of data or configurations within adomain data table to be implemented. For instance, the modification madeby the user may be implemented and the user interface for which themodification was requested may be updated dynamically. Accordingly, anyupdates or changes to a user interface may be quickly put out to theusers of the system. In some examples, refreshing the master controltable may be performed automatically upon changes being detected,completed, or the like. For instance, in step 620, the modified userinterface may be displayed to the plurality of users accessing thesystem in response to the master control table being refreshed.

The systems and arrangements described herein provide a quick, efficientand dynamic way to modify user interfaces without requiring coding ofeach change (or each domain data table). Rather, changes may beimplemented via the master control table and the changes may be quicklyput into effect. This aids in standardizing and controlling changes madeto domain data tables, user interfaces, and the like, and provides anefficient way to dynamically modify user interfaces.

FIGS. 7A and 7B illustrate an example user interface that may be used tomodify domain data via the master control table according to one or moreaspects discussed herein. FIG. 7A illustrates one example user interfacethat may be generated. The user interface 700 includes a first portion702 and a second portion 704. As shown in FIG. 7A, the first portion ispopulated with a listing of all data tables associated with the mastercontrol table. In some examples, the master control table itself mayalso be listed in the first portion such that modifications to themaster control table, adding additional records to the master controltable, and the like, may be made via the system and framework as well.

In some examples, populating the first portion 702 of the master controltable may include reading all domain data tables from the master controltable including the configurations and structure, definitions, and thelike, of each domain data table. Accordingly, upon populating the firstportion 702, all data associated with each data table may have been readby the master control table and may be available for display, editing,or the like, as desired.

Each domain data table (including, in at least some examples, the mastercontrol table) provided in the first portion 702 may be selectable. Forinstance, clicking or double clicking on a name of a domain data tablemay select the data table. Selection of a domain data table may causethe second portion 704 to be populated.

For instance, as shown in FIG. 7B, both the first portion 702 and thesecond portion 704 in the user interface 700 have been populated.Population of the second portion 704 may be based on the domain datatable selected from the first portion. That is, selection of a domaindata table may cause the second portion to populate with not only thedata associated with that table but also any definitions, structure,configurations, or the like. For instance, since the master controltable has read or retrieved the data and configuration for each table,the selected table may be displayed with all associated configurationsin the second portion 704.

Edits and/or modifications to the selected domain data table may beperformed in the second portion of the user interface 700. For instance,a user may select (e.g., click or double click on) a particular column,row, data entry, cell, or the like and a modification may be made. Insome examples, selection of a desired item for modification may cause asecond user interface to display (e.g., overlaying a portion of thefirst user interface) and edits may be made via the second userinterface. Additionally or alternatively, a user may select “EDIT”option 710 to enable editing of domain data. For instance, in someexamples, a user may select “EDIT” option 710 and the second userinterface discussed above may appear (e.g., overlaying the modificationuser interface) and enabling a user to modify the domain data.

Interface 700 in FIG. 7B further includes an “ADD” option 706. Selectionof option 706 may cause a second interface to display. The secondinterface may, in some examples, overlay the first interface and mayinclude one or more fields for adding a record to the selected domaindata table. For instance, the second user interface may include a fieldcorresponding to each column of the selected domain data table for whicha record is being added. Accordingly, the second user interface may bedynamically generated and a format of the user interface may vary basedon the configurations of the domain data table selected (e.g., to whicha record is being added).

Interface 700 further includes “REFRESH” option 708. Option 708 may beselected upon completion of one or more edits, modifications, or thelike. Selection of option 708 may cause the master control table toupdate, thereby implementing any changes made to the selected domaindata table. Accordingly, a user interface associated with the modifieddomain data table may be updated (e.g., regenerated) to reflect anychanges made. Accordingly, changes to a user interface (or associateddomain data) may be made dynamically without requiring coding changes toone or more domain data tables.

In some arrangements, the second portion 704 may include multiple pagesof data. Accordingly, a user interface 700 may include region 712indicating a page of data being displayed, a number of pages available,and/or options to move between pages (e.g., selectable arrows for movingbetween pages).

In some examples, the master control table may be searchable. That is, auser may search for a particular domain data table by inserting a name(or portion of a name) of the data table into a search bar. Further, aselected domain data table (e.g., displayed in the second portion 704)may also be searchable. Accordingly, any field, column, data, or thelike, may be used as a search criteria to identify one or more records,definitions, or the like.

One or more aspects of the disclosure may be embodied in computer-usabledata or computer-executable instructions, such as in one or more programmodules, executed by one or more computers or other devices to performthe operations described herein. Generally, program modules includeroutines, programs, objects, components, data structures, and the likethat perform particular tasks or implement particular abstract datatypes when executed by one or more processors in a computer or otherdata processing device. The computer-executable instructions may bestored on a computer-readable medium such as a hard disk, optical disk,removable storage media, solid-state memory, RAM, and the like. Thefunctionality of the program modules may be combined or distributed asdesired in various embodiments. In addition, the functionality may beembodied in whole or in part in firmware or hardware equivalents, suchas integrated circuits, application-specific integrated circuits(ASICs), field programmable gate arrays (FPGA), and the like. Particulardata structures may be used to more effectively implement one or moreaspects of the disclosure, and such data structures are contemplated tobe within the scope of computer executable instructions andcomputer-usable data described herein.

Various aspects described herein may be embodied as a method, anapparatus, or as one or more computer-readable media storingcomputer-executable instructions. Accordingly, those aspects may takethe form of an entirely hardware embodiment, an entirely softwareembodiment, an entirely firmware embodiment, or an embodiment combiningsoftware, hardware, and firmware aspects in any combination. Inaddition, various signals representing data or events as describedherein may be transferred between a source and a destination in the formof light or electromagnetic waves traveling through signal-conductingmedia such as metal wires, optical fibers, or wireless transmissionmedia (e.g., air or space). In general, the one or morecomputer-readable media may comprise one or more non-transitorycomputer-readable media.

As described herein, the various methods and acts may be operativeacross one or more computing servers or platforms and one or morenetworks. The functionality may be distributed in any manner, or may belocated in a single computing device (e.g., a server, a client computer,and the like). In such arrangements, any and/or all of theabove-discussed communications between computing platforms maycorrespond to data being accessed, moved, modified, updated, and/orotherwise used by the single computing platform. Additionally oralternatively, the computing platform discussed above may be implementedin one or more virtual machines that are provided by one or morephysical computing devices. In such arrangements, the various functionsof each computing platform may be performed by the one or more virtualmachines, and any and/or all of the above-discussed communicationsbetween computing platforms may correspond to data being accessed,moved, modified, updated, and/or otherwise used by the one or morevirtual machines.

Aspects of the disclosure have been described in terms of illustrativeembodiments thereof. Numerous other embodiments, modifications, andvariations within the scope and spirit of the appended claims will occurto persons of ordinary skill in the art from a review of thisdisclosure. For example, one or more of the steps depicted in theillustrative figures may be performed in other than the recited order,and one or more depicted steps may be optional in accordance withaspects of the disclosure.

What is claimed is:
 1. A method, comprising: generating, by a domaindata modification computing platform, a master control table, the mastercontrol table including each domain data table of a plurality of domaindata tables and including a configuration associated with each domaindata table of the plurality of domain data tables; receiving, by thedomain data modification computing platform, a request to modify atleast one domain data table of the plurality of domain data tables;responsive to receiving the request to modify the at least one domaindata table, generating, by the domain data modification computingplatform, a first user interface having a first portion and a secondportion; populating, by the domain data modification computing platform,the first portion of the generated first user interface with a listingof the plurality of domain data tables, populating the first portionincluding retrieving, from the master control table, the plurality ofdomain data tables and associated configuration of each domain datatable in the plurality of domain data tables; receiving, by the domaindata modification computing platform, user input selecting the at leastone domain data table from the listing of the plurality of domain datatables provided in the first portion; responsive to receiving the userinput, populating, by the domain data modification computing platform,the second portion of the first user interface including displaying theselected at least one domain data table and the associatedconfiguration; receiving, by the domain data modification computingplatform, user input modifying the selected at least one domain datatable via the second portion of the first user interface; refreshing, bythe domain data modification computing platform, the master controltable to implement the received user input modifying the selected atleast one domain data table; and generating, by the domain datamodification computing platform a second user interface including themodification made to the at least one domain data table.
 2. The methodof claim 1, further including: prior to generating the master controltable, receiving, by the domain data modification computing platform, aplurality of domain data tables; and formatting, by the domain datamodification computing platform, the plurality of domain data tables tobe read by the master control table.
 3. The method of claim 2, whereinformatting the plurality of domain data tables further includes:evaluating, by the domain data modification computing platform, eachdomain data table of the plurality of domain data tables to identify oneor more data tables having a format that is not compatible with themaster control table; and reformatting the identified one or more datatables to have a format compatible with the master control table.
 4. Themethod of claim 1, wherein the second user interface is a user interfaceassociated with data from the selected at least one domain data table.5. The method of claim 4, wherein the second user interface is a userinterface associated with at least one of: an on-line application and amobile application.
 6. The method of claim 1, further including:authenticating, by the domain data modification computing platform, auser requesting to modify the at least one domain data table.
 7. Themethod of claim 1, wherein the request to modify the at least one domaindata table includes a request to modify at least one of: a setting and amenu option.
 8. The method of claim 1, wherein the associatedconfiguration of each domain data table includes at least one of: anumber of columns in the domain data table, a type of data in the domaindata table, and definitions associated with the domain data table.
 9. Adomain data modification computing platform, comprising: at least afirst processor; a first communication interface communicatively coupledto the at least a first processor; and a first memory storingcomputer-readable instructions that, when executed by the at least afirst processor, cause the domain data modification computing platformto: generate a master control table, the master control table includingeach domain data table of a plurality of domain data tables andincluding a configuration associated with each domain data table of theplurality of domain data tables; receive a request to modify at leastone domain data table of the plurality of domain data tables; responsiveto receiving the request to modify the at least one domain data table,generate a first user interface having a first portion and a secondportion; populate the first portion of the generated first userinterface with a listing of the plurality of domain data tables,populating the first portion including retrieving, from the mastercontrol table, the plurality of domain data tables and associatedconfiguration of each domain data table in the plurality of domain datatables; receive user input selecting the at least one domain data tablefrom the listing of the plurality of domain data tables provided in thefirst portion; responsive to receiving the user input, populate thesecond portion of the first user interface including displaying theselected at least one domain data table and the associatedconfiguration; receive user input modifying the selected at least onedomain data table via the second portion of the first user interface;refresh the master control table to implement the received user inputmodifying the selected at least one domain data table; and generate asecond user interface including the modification made to the at leastone domain data table.
 10. The domain data modification computingplatform of claim 9, further including instructions that, when executed,cause the domain data modification computing platform to: prior togenerating the master control table, receive a plurality of domain datatables; and format the plurality of domain data tables to be read by themaster control table.
 11. The domain data modification computingplatform of claim 10, wherein formatting the plurality of domain datatables further includes: evaluating each domain data table of theplurality of domain data tables to identify one or more data tableshaving a format that is not compatible with the master control table;and reformatting the identified one or more data tables to have a formatcompatible with the master control table.
 12. The domain datamodification computing platform of claim 9, wherein the second userinterface is a user interface associated with data from the selected atleast one domain data table.
 13. The domain data modification computingplatform of claim 12, wherein the second user interface is a userinterface associated with at least one of: an on-line application and amobile application.
 14. The domain data modification computing platformof claim 9, further including instructions that, when executed, causethe domain data modification computing platform to: authenticate a userrequesting to modify the at least one domain data table.
 15. The domaindata modification computing platform of claim 9, wherein the request tomodify the at least one domain data table includes a request to modifyat least one of: a setting and a menu option.
 16. The domain datamodification computing platform of claim 9, wherein the associatedconfiguration of each domain data table includes at least one of: anumber of columns in the domain data table, a type of data in the domaindata table, and definitions associated with the domain data table. 17.One or more non-transitory computer-readable media storing instructionsthat, when executed by a computer system comprising at least oneprocessor, memory, and a communication interface, cause the computersystem to: generate, by a domain data modification computing platform, amaster control table, the master control table including each domaindata table of a plurality of domain data tables and including aconfiguration associated with each domain data table of the plurality ofdomain data tables; receive, by the domain data modification computingplatform, a request to modify at least one domain data table of theplurality of domain data tables; responsive to receiving the request tomodify the at least one domain data table, generate, by the domain datamodification computing platform, a first user interface having a firstportion and a second portion; populate, by the domain data modificationcomputing platform, the first portion of the generated first userinterface with a listing of the plurality of domain data tables,populating the first portion including retrieving, from the mastercontrol table, the plurality of domain data tables and associatedconfiguration of each domain data table in the plurality of domain datatables; receive, by the domain data modification computing platform,user input selecting the at least one domain data table from the listingof the plurality of domain data tables provided in the first portion;responsive to receiving the user input, populate, by the domain datamodification computing platform, the second portion of the first userinterface including displaying the selected at least one domain datatable and the associated configuration; receive, by the domain datamodification computing platform, user input modifying the selected atleast one domain data table via the second portion of the first userinterface; refresh, by the domain data modification computing platform,the master control table to implement the received user input modifyingthe selected at least one domain data table; and generate, by the domaindata modification computing platform a second user interface includingthe modification made to the at least one domain data table.
 18. The oneor more non-transitory computer-readable media of claim 17, furtherincluding instructions that, when executed, cause the computer systemto: prior to generating the master control table, receive, by the domaindata modification computing platform, a plurality of domain data tables;and format, by the domain data modification computing platform, theplurality of domain data tables to be read by the master control table.19. The one or more non-transitory computer-readable media of claim 18,wherein formatting the plurality of domain data tables further includes:evaluating, by the domain data modification computing platform, eachdomain data table of the plurality of domain data tables to identify oneor more data tables having a format that is not compatible with themaster control table; and reformatting the identified one or more datatables to have a format compatible with the master control table. 20.The one or more non-transitory computer-readable media of claim 17,wherein the associated configuration of each domain data table includesat least one of: a number of columns in the domain data table, a type ofdata in the domain data table, and definitions associated with thedomain data table.